Health Cloud Diagnostics System API - Implementation Template

(0 reviews)

Field mapping

Observation

FHIR Field NameSalesforce ObjectSalesforce Field NameNotes
Identifier.useIdentifierIdUsageTypeThe identifier information for a health condition is represented as Identifier records that reference the health condition record using their Identifier.ParentRecordId field.
Identifier.systemIdentifierSourceSystem
Identifier.valueIdentifierIdValue
Identifier.type.coding.codeIdentifierIDTypeId
basedOnCareObservationBasedOnIdWhile FHIR defines observation.basedOn as a zero-to-many reference, the Salesforce implementation is a zero-to-one text field
partOfCareObservationPartOfIdWhile FHIR defines observation.partOf as a zero-to-many reference, the Salesforce implementation is a zero-to-one text field
category.coding.codeCareObservationCategoryWhile FHIR defines observation.category as a zero-to-many reference to code set bundle, the Salesforce implementation is a zero-to-one picklist.
statusCareObservationObservationStatusWhile FHIR defines observation.status as a reference to code set bundle, the Salesforce implementation is a picklist.
code.coding.codeCareObservationCodeIdWhile FHIR defines observation.code as a one-to-one reference to code set bundle, Salesforce implements this as three separate CodeSet reference fields
subjectCareObservationObservedSubjectIdThe Salesforce implementation of observation.subject supports references to only patients.
encounterCareObservationEncounterId
effective.effectiveDateTimeCareObservationEffectiveDateTime
effectivePeriod.startCareObservationEffectiveDateTimeBecause Salesforce doesn’t support a native period data type, the observation.effective.effectivePeriod field is flattened into a set of effective date and end date fields.
effectivePeriod.endCareObservationEndDateTime
issuedCareObservationIssuedDateTimeBecause Salesforce doesn’t support a native instant data type, the observation. issued FHIR resource is implemented as a date time field in Salesforce.
performerCareObservationObserverIdWhile FHIR defines observation.performer as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference to Account and Healthcare Provider.
resultsInterpreterCareObservationInterpretedByIdWhile FHIR defines observation.resultsInterpreter as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference to CarePerformer.
valueQuantity.valueCareObservationObservedValueTypeA Salesforce-original field that determines whether the value stored in CareObservation.ObservedValueNumerator and CareObservation.ObservedValueDenominator is a range, ratio, or quantity. This field is used only when the data entered for observation.value is one these data types.
valuePeriod.startCareObservationObservationStartTimeCareObservation.ObservationStartTime is used for both observation.component.value.valueDateTime and observation.component.value.valuePeriod. Because Salesforce doesn’t support a native period data type, the observation.value.valuePeriod FHIR resource is flattened to a set of start and end dates.
valuePeriod.endCareObservationObservationEndTime
valueCodeableConcept.coding.codeCareObservationObservedValueCodeId
valueRatio.numerator.valueCareObservationObservedValueNumeratorBecause Salesforce doesn’t support native range, ratio, and quantity data types, the observation.value FHIR resource is flattened to a set of numerator, denominator, and unit fields for this type of data.
valueRatio.denominator.valueCareObservationObservedValueDenominator
valueBooleanCareObservationIsOutcomePositiveCareObservation.IsObserved is a duplicate field that can store the same information. Use only one of these two fields.
valueStringCareObservationObservedValueText
interpretation.coding.codeCareObservationValueInterpretationWhile FHIR defines observation.interpretation as a zero-to-many code set bundle, the Salesforce implementation is a zero-to-one picklist.
bodySite.coding.codeCareObservationBodySiteId
method.coding.codeCareObservationMethodId
deviceCareObservationDeviceIdReferences to device metrics records aren’t supported.
referenceRange.low.valueCareObservationLowerBaselineValueBecause Salesforce doesn’t support a native quantity data type, the observation.referenceRange.low FHIR resource is flattened to a set of value and unit fields for this type of data.
referenceRange.low.unitCareObservationBaselineUnitId
referenceRange.high.valueCareObservationUpperBaselineValueBecause Salesforce doesn’t support a native quantity data type, the observation.referenceRange.high FHIR resource is flattened to a set of value and unit fields for this type of data.
referenceRange.textCareObservationBaselineValueText
hasMemberCareObservationRelatedObservationIdWhile FHIR defines observation.hasMember as a zero-to-many resource, the Salesforce implementation is zero-to-one. Only references to observation records are supported.
component.code.coding.codeObservationComponentComponentTypeCodeId
component.valueQuantity.valueObservationComponentValueTypeA Salesforce-original field that determines whether the value stored in CareObservationComponent.ObservedValueNumerator and CareObservationComponent.ObservedValueDenominator is a range, ratio, or quantity. This field is used only when the data entered for observation.component.value is one these data types.
component.valueQuantity.unitObservationComponentObservedValueUnitId
component.valuePeriod.startObservationComponentObservationStartTimeCareObservationComponent.ObservationStartTime is used for both observation.component.value.valueDateTime and observation.component.value.valuePeriod. Because Salesforce doesn’t support a native period data type, the observation.component.value.valuePeriod FHIR resource is flattened to a set of start and end dates.
component.valuePeriod.endObservationComponentObservationEndTime
component.valueCodeableConcept.coding.codeObservationComponentObservedValueCodeId
component.valueRatio.numerator.valueObservationComponentObservedValueNumeratorBecause Salesforce doesn’t support native range, ratio, and quantity data types, the observation.component.value FHIR resource is flattened to a set of numerator, denominator, and unit fields for this type of data. The Salesforce implementation of observation.component.value doesn’t support observation.component.value.valueSampleData and observation.component.value.valueTime.
component.valueRatio.denominator.valueObservationComponentObservedValueDenominator
component.valueBooleanObservationComponentIsObserved
component.valueStringObservationComponentObservedValueText
component.dataAbsentReasonObservationComponentMissingDataReasonWhile FHIR defines observation.component.dataAbsentReason as a code set bundle reference, the Salesforce implementation is a text field.
component.interpretation.coding.codeObservationComponentValueInterpretationWhile FHIR defines observation.component.interpretation as a code set bundle reference, the Salesforce implementation is a picklist.
component.referenceRange.low.valueObservationComponentLowerBaselineValue
component.referenceRange.low.unitObservationComponentBaselineUnitId
component.referenceRange.high.valueObservationComponentUpperBaselineValue
component.referenceRange.textObservationComponentBaselineValueText

DiagnosticReport

FHIR Field NameSalesforce ObjectSalesforce Field NameNotes
Identifier.useIdentifierIdUsageTypeThe identifier information for a health condition is represented as Identifier records that reference the health condition record using their Identifier.ParentRecordId field.
Identifier.systemIdentifierSourceSystem
Identifier.valueIdentifierIdValue
Identifier.type.coding.codeIdentifierIDTypeId
basedOnDiagnosticSummaryBasedOnIdWhile FHIR defines diagnosticReport.basedOn as a zero-to-many reference, the Salesforce implementation is a zero-to-one text field.
statusDiagnosticSummaryStatusWhile FHIR defines diagnosticReport.status as a reference to code set bundle, the Salesforce implementation is a picklist.
category.coding.codeDiagnosticSummaryCategoryWhile FHIR defines diagnosticReport.category as a reference to code set bundle, the Salesforce implementation is a multi-select picklist.
code.coding.codeDiagnosticSummaryCodeId
subjectDiagnosticSummaryPatientIdThe Salesforce implementation of diagnosticReport.subject supports references to only patients
encounterDiagnosticSummaryClinicalEncounterId
effective.effectiveDateTimeDiagnosticSummaryEffectiveStartDateTime
effectivePeriod.startDiagnosticSummaryEffectiveStartDateTimeBecause Salesforce doesn’t support a native period data type, the diagnosticReport.effective.effectivePeriod field is flattened into a set of start date and end date fields.
effectivePeriod.endDiagnosticSummaryEffectiveEndDateTime
issuedDiagnosticSummaryIssuedDateTimeBecause Salesforce doesn’t support a native instant data type, the diagnosticReport.issued FHIR resource is implemented as a date time field in Salesforce.
performerDiagnosticSummaryIssuedByIdWhile FHIR defines diagnosticReport.performer as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference to CarePerformer.
resultDiagnosticSummaryCareObservationIdWhile FHIR defines diagnosticReport.result as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference to CareObservation
conclusionCode.coding.codeDiagnosticSummarySummaryCodeIdWhile FHIR defines diagnosticReport.conclusionCode as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference.
presentedFormDiagnosticSummaryReportAttachmentIdWhile FHIR defines diagnosticReport.conclusionCode as a zero-to-many resource, the Salesforce implementation is a zero-to-one reference.

Reviews

TypeTemplate
OrganizationMulesoft
Published by
MuleSoft Organization
Published onDec 14, 2022
Asset overview

Asset versions for 1.0.x

Asset versions
VersionActions
1.0.5